On Fri, 3 Jul 2020 02:31:57 -0400, JF Mezei wrote:
> Xcode was able to generate ARM binaries for quite some time because it
> could create IOS apps. So no groundwork really needed to allow Mac to
> move to ARM
Hi JF Mezei,
Given you're not an apologist, a normal adult conversation can ensue,
simply because you're not bent on claiming all facts about Apple are "lies
by liars", & you don't refute obvious facts simply because you don't like
them, & you don't brazenly fabricate imaginary functionality, and you don't
incessantly play silly childish pedantic games around quoted semantics,
etc.
You are correct on Xcode, where the article concurs, saying:
"While Apple may not have specifically had an ARM Mac in mind when
it released Xcode, the unified IDE... was still the first initial
step toward such a device. Without a centralized development
environment for macOS, the current transition — and the previous
shift to Intel — just wouldn't be possible."
> OpenGL has exised for quite some time.
You're again correct that it's not so much that OpenGL existed, but that it
was _deprecated_, as explained in the quote below:
"The introduction of Metal on iOS in 2014 - and ultimate deprecation of
OpenGL in 2018 - introduced a new layer of independence for Apple
developers."
> Metal isn't so much an enabled of Macs moving o ARM, but rather Macs
> moving to Apple's proprietary GPUs for Macs.
Again, you appear to be correct, based on what the article surmised:
"By using Metal, both macOS and iOS developers could code to this
specific API and allow their apps to function regardless of what GPU
is present."
> SIP is only indirectly part of it, as a move to reduce 3rd party system
> software and kernel extensions.
You skipped "Swift", where this is what they said about it:
"Apple believes that having a single coding language for apps across iOS,
macOS and Apple's other platforms is going to make optimization and
performance better across the board."
As for SIP, again you're correct, showing you have a good overall grasp:
"While System Integrity Protection did bolster security, it did do away
with some of the UNIX-like system functions that macOS had for years.
And by doing so, it took macOS a step toward its other operating systems
which are, importantly, already designed for ARM.
> T-Series chips are more part of "Back to mac" with OS-X getting more
> IUOS features than more to ARM. These T2 worked under Intel Macs.
While it's interesting that the T-Series is called "ARM-based silicon" in
this article (as opposed to the ridiculously desperate non-ARM trademark
Apple expects us to employ moving forward), Apple Insider suggested it was
a "test run" of the ARM based Macs to come:
"it also appears as a sort of test run for integrating ARM technology in
X86 Macs. The T-series chips are purpose-built, customized chips
specifically designed for Macs. With a switch to ARM-based CPUs,
there are opportunities for even further integration, especially since
Apple could ditch the T2 chip and bake its features directly into an
ARM system-on-chip (SoC)."
NOTE: Luckily, Apple Insider didn't use the ridiculously desperate term
Apple now wants us to use, but likely, perhaps, only because Apple
hadn't frantically coined the new term at that article's debut.
> Death of 32 bit apps is definitely part of the move since it allows
> Rosetta to not handle 32 bit calls and map them to 64 bit ARM calls.
Again, you're on the mark as it appears it killed a lot of code that no
longer needs to be ported to the new Mac ARM computers:
"It's especially important because it spelled the end of all the
legacy 32-bit code that Macs have been running for years."
NOTE: Of course, that "could" mean loss of functionality for users,
depending on whether they had legacy 32-bit code they needed.
> Catalysts has nothing to do with the move to ARM, it has more to do with
> "Back to Mac".
As you noted, and as Apple Insider noted:
"it did lay a foundation for apps that could be optimized for an
ARM environment."
> However, it has a big advantage n that an IOS app
> compiled for iPhone should run on a Mac.
Not only iOS, but the article implies that even the X86 ports are easier:
"Catalyst makes it easy for developers to create apps that can work
on both ARM and x86 architecture."
"That's something that could smooth the transition for developers and
consumers alike, since it'll make porting apps to an ARM-optimized
version of macOS as easy as porting one from iPad to Mac."
"This will save developers time and hassle, particularly since the
overall transition to ARM-based Macs isn't going to be a short one."
--
Usenet works best when helpful adults share ideas politely with each other.